bump dbt-utils to 1.4.1 across all subprojects - #9927
Open
a-monteiro wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
WIP
a-monteiro
marked this pull request as ready for review
August 8, 2026 14:13
PR SummaryLow Risk Overview
Reviewed by Cursor Bugbot for commit 7b50cce. Configure here. |
github-actions
Bot
added
ready-for-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dbt-utils has been pinned at 1.3.0 in all five subprojects since Aug 2024. This bumps it to 1.4.1 (latest, 2026-06-28) and regenerates the five checked-in lock files.
Low-risk by inspection of the upstream diff: only six macro files changed between 1.3.0 and 1.4.1 (recency, unique_combination_of_columns, date_spine, get_filtered_columns_in_relation, star, union).
generate_surrogate_key— the only changed-macro candidate used inside model bodies here (121 call sites) — is untouched, so nostate:modifiedrebuild wave. The changed macros we use are generic tests, which get a one-time modified flag.What it buys: dbt 2.x forward-compatibility (1.3.0's
require-dbt-versionrefuses dbt 2.x; 1.3.2 widened it to<3.0.0) and a Fusion Jinja fix inunique_combination_of_columns, our most-used macro (4700+ uses). No model code changes needed.tokens' codegen and trino_utils pins are deliberately untouched.